Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1644

reference: 965-tree-1
name: 1644
tree-preservation-order: undefined
965-tpo-1
uprn
address-text
point: POINT (-0.996991 50.855160)
geometry: MULTIPOLYGON (((-0.996948 50.855156,-0.996950 50.855164,-0.996956 50.855172,-0.996965 50.855178,-0.996977 50.855182,-0.996990 50.855183,-0.997004 50.855182,-0.997016 50.855178,-0.997025 50.855172,-0.997031 50.855165,-0.997034 50.855156,-0.997032 50.855148,-0.997026 50.855141,-0.997016 50.855134,-0.996992 50.855129,-0.996978 50.855130,-0.996966 50.855134,-0.996957 50.855140,-0.996951 50.855147,-0.996948 50.855156)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL